Allow use of TLS without custom/self-signed certificate chain #349
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bj00rn
force-pushed
the
chore/allow-tls-without-custom-ca
branch
2 times, most recently
from
2b0ec29 to
d8c8931
Compare
nanomad
previously approved these changes
Jun 17, 2025
Contributor
|
@bj00rn Please solve the merge conflicts |
bj00rn
force-pushed
the
chore/allow-tls-without-custom-ca
branch
from
d8c8931 to
47feb82
Compare
Author
done |
nanomad
approved these changes
Jun 18, 2025
nanomad
requested changes
Jun 18, 2025
bj00rn
force-pushed
the
chore/allow-tls-without-custom-ca
branch
from
45d45d1 to
11371c4
Compare
nanomad
approved these changes
Jun 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow secure connections over TLS without providing self signed certificate chain.
fixes #347